View S27KL0641DABHI023_8477442.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

cypress semiconductor corporation ? 198 champion court ? san jose , ca 95134-1709 ? 408-943-2600 document number: 001-97964 rev. *e revised march 01, 2016 s27kl0641, s27ks0641 hyperram ? self-refresh dram 3.0v/1.8v 64 mb (8 mb) advance distinctive characteristics hyperbus? low signal count interface ? 3.0v i/o, 11 bus signals ? single ended clock (ck) ? 1.8v i/o, 12 bus signals ? differential clock (ck, ck#) ? chip select (cs#) ? 8-bit data bus (dq[7:0]) ? read-write data strobe (rwds) ? bidirectional data strobe / mask ? output at the start of all tran sactions to indicate refresh latency ? output during read transactions as read data strobe ? input during write transactions as write data mask high performance ? up to 333mb/s ? double-data rate (ddr) - two data transfers per clock ? 166-mhz clock rate (333 mb/s) at 1.8v v cc ? 100-mhz clock rate (200 mb/s) at 3.0v v cc ? sequential burst transactions ? configurable burst characteristics ? wrapped burst lengths: ? 16 bytes (8 clocks) ? 32 bytes (16 clocks) ? 64 bytes (32 clocks) ? 128 bytes (64 clocks) ? linear burst ? hybrid option - one wrapped burst followed by linear burst ? wrapped or linear burst type selected in each transaction ? configurable output drive strength ? package and die options ? 24-ball fbga footprint performance summary cs# ck# ck dq[7:0] rwds v ss v ss q v cc v cc q reset# read transaction timings maximum clock rate at 1.8v v cc /v cc q 166 mhz maximum clock rate at 3.0v v cc /v cc q 100 mhz maximum access time, (t acc at 166 mhz) 36 ns maximum cs# access time to first word at 166 mhz (excluding refresh latency) 56 ns maximum current consumption burst read or write (linear burst at 166 mhz, 1.8v) 60 ma power on reset 50 ma standby (cs# = high, 3v, 105 c) 300 a deep power down (cs# = high, 3v, 105 c) 40 a standby (cs# = high, 1.8v, 105 c) 300 a deep power down (cs# = high, 1.8v, 105 c) 20 a errata: for information on silicon errata, see "errata? on page 27 . details include trigger conditions, dev ices affected, and proposed workaround.
document number: 001-97964 rev. *e page 2 of 29 s27kl0641, s27ks0641 advance contents 1. general description ..................................................... 3 2. hyperram product overview ..................................... 4 3. hyperbus interface ...................................................... 5 3.1 command-address bit assignments ............................. 5 3.2 read transactions......................................................... 6 3.3 write to memory space tran sactions............................ 6 4. memory space .............................................................. 7 5. register space ............................................................. 7 5.1 device identification registers....................................... 7 5.2 register space access.................................................. 8 hyperram hardware interface 6. interface states .......................................................... 15 6.1 power conservation modes......................................... 15 7. electrical specifications ............................................ 17 7.1 absolute maximum ratings .... ...................................... 17 7.2 latchup characteristics ........ ........... ........... ........... ....... 18 7.3 operating ranges......................................................... 18 7.4 dc characteristics ........................................................ 18 7.5 power-up initializa tion .................................................. 20 7.6 power down ................................................................. 21 7.7 hardware reset ............................................................ 22 8. timing specifications ................................................. 23 8.1 ac characteristics ........................................................ 23 9. physical interface ....................................................... 25 10. ordering information .................................................. 25 10.1 ordering part number................................................... 25 10.2 valid combinations ....................................................... 26 11. errata ............................................................................ 27 12. revision history .......................................................... 28
document number: 001-97964 rev. *e page 3 of 29 s27kl0641, s27ks0641 advance 1. general description the spansion hyperram tm family of products are high-spee d cmos, self-refresh dynamic ram (dram) devices, with a hyperbus interface. the random access memory (ram) array uses dynamic cells that r equire periodic refresh. refresh control logic within the device manages the refresh operations on the ram a rray when the memory is not being actively read or written by the hyperbus interface master (host). since the host is not required to manage any refresh operations, the dram array appears to the host as though th e memory uses static cells that retain data without refresh. hence, the memory can also be described as pseudo static ram (psram). because the dram cells cannot be refreshed during a read or writ e transaction, there is a requirement that the host not perform read or write burst transfers that are long enough to block the necessary internal logic refresh operations when they are neede d. the host is required to limit the duration of transactions and allow additional initial access latency, at the beginning of a new t ransaction, if the memory indicates a refresh operation is needed. hyperbus is a low signal count, double data rate (ddr) interf ace, that achieves high speed read and write throughput. the ddr protocol transfers two data bytes per clock cycle on the dq inpu t/output signals. a read or write transaction on hyperbus consi sts of a series of 16-bit wide, one clock cycle data transfers at th e internal hyperram core with two corresponding 8-bit wide, one-ha lf- clock-cycle data transfers on the dq signals . all inputs and outputs are lv-cmos compat ible. ordering part number (opn) device versions are available for core (v cc ) and io buffer (v cc q) supplies of either 1.8v or 3.0v (nominal). command, address, and data information is transferred over t he eight hyperbus dq signals. the clock is used for information capture by a hyperbus device when receiving command-address/da ta on the dq signals. command-address values are center aligned with clock edges. the read/write data strobe (rwds) is a bidirectional signal that indicates: ? when data will start to transfer from the memory to the host in read transactions (initial read latency), ? when data is being transferred from the memory to the host dur ing read data transfers (source sy nchronous read data strobe), ? when data will start to transfer from the host to the me mory in write transactions (initial write latency), ? and data masking during write data transfers. during the command and address cycles of a read or write tran saction, rwds acts as an output from the memory to indicate whether additional initial access latency is needed to perform a dynamic memory refresh operation. during read data transfers, rwds is a read data strobe with data values edge aligned with the transitions of rwds driven by the memory device. during write data transfers, rwds indicates whether a data byte is masked (prevented from changing the byte location in memory) or not masked (written to memory). data masking may be used by the host to byte ali gn write data within the memory or to enable merging of multiple non-word aligned writes in a single burst write. during write tran sactions, data is center aligned with the clock. read and write transactions are burst orie nted, transferring the next sequential word during each clock cycle. each individual read or write transaction can use either a wr apped or linear burst sequence. during wrapped transactions, accesse s start at a select ed location and continue to the end of a conf igured word group aligned boundary, then wrap to the beginning location in the group, then continue back to the starting location. wrapped bursts are general ly used for critical word first instruction or data cache lin e fill read accesses. during linear transactions, accesses start at a select ed location and continue in a sequential manner until the trans action is terminated when cs# returns high. linear transactions are gener ally used for large contiguous data transfers such as graphic image moves. since each transaction command selects the type of burst sequence for that access, wrapped and linear burst transactions can be dynamically intermixed as needed. for additional information on hyperbus interface operat ion, please refer to the hyperbus specification.
document number: 001-97964 rev. *e page 4 of 29 s27kl0641, s27ks0641 advance 2. hyperram product overview the hyperram family consists of multip le density option, 1.8v or 3.0v core and i/o, synchronous self-refresh dynamic ram (dram) memory devices. this family provides a hyperbus slave interface to the host system. hype rbus has an 8 bit (1 byte) wide ddr data bus and uses only word-wide (16-bit data) address b oundaries. read transactions prov ide 16 bits of data during each clock cycle (8 bits on both clock edges). writ e transactions take 16 bits of data from each clock cycle (8 bits on each clock edge ). figure 2.1 hyperram interface read and write transactions require two clock cycles to define the target row address and burst type, then an initial access la tency of t acc . during the command-address (ca) part of a transaction, the memo ry will indicate whether an additional latency for a required refresh time (t rfh ) is added to the initial latency; by driving the rwds signa l to the high state. during the ca period the third clock cycle will specify the target word address wit hin the target row. during a read (or write) trans action, after the initial data value has been output (or input), additional data can be read from (or written to) the row on s ubsequent clock cycles in either a wrapped or linear sequence. when configured in linear burst mode, the device will automatically fe tch the next sequential row from the mem ory array to support a continuous linear burst. simultaneously accessing the next row in t he array while the read or write data tra nsfer is in progress, allows for a linear sequential burst operation that can provide a sustained data rate of 333 mb/s (1 byte (8 bit dat a bus) * 2 (data clock edges) * 166 mhz = 333 mb/s). cs# ck# ck dq[7:0] rwds v ss v ss q v cc v cc q reset#
document number: 001-97964 rev. *e page 5 of 29 s27kl0641, s27ks0641 advance 3. hyperbus interface for the general description of how the hyperbus interface operate s in hyperram memories, refer to the hyperbus specification. the following section describes hyperram device dependent aspects of hyper bus interface operation. all bus transactions can be classified as either read or write. a bus transaction is started wit h cs# going low with ck = low a nd ck# = high. the transaction to be perform ed is presented to the hyperram device duri ng the first three clock cycles in a ddr manner using all six clo ck edges. these first three clocks tran sfer three words of command / a ddress (ca0, ca1, ca2) informatio n to define the transaction characteristics: ? read or write transaction ? whether the transaction will be to the memory array or to register space. ? whether a read transaction will use a linear or wrapped burst sequence ? the target half-page address (row and upper order column address) ? the target word (within half-page) add ress (lower order column address) once the transaction has be en defined, a number of id le clock cycles are used to satisfy in itial read or write access latency requirements before data is transferred. during the command-addre ss portion of all transactions, rwds is used by the memory to indicate whether additional initial access latency will be inserted for a required refresh of the memory array. when data transfer begins, read data is edge aligned with rwds transitions or write data is center aligned with clock transitio ns. during read data transfer, rwds serves as a source synchronous data timing strobe. during write data transfer, clock transition s provide the data timing reference and rwds is used as a data mask . when rwds is low during a write data transfer, the data byte is written into memory; if rwds is high du ring the transfer the byte is not written. data is transferred as 16-bit values with the first eight bits tr ansferred on a high going ck (write data or ca bits) or rwds e dge (read data) and the second eight bits being transferred on the low going ck or rwds edge. data transfers during read or write operations can be ended at any time by bringing cs# high when ck = low and ck# = high. the clock may stop in the idle state while cs# is high. the clock may also stop in the idle state for short periods whil e cs# is low, as long as this does not cause a transaction to e xceed the cs# maximum time low (t csm ) limit. this is referred to as active clock stop m ode. in some hyperbus devi ces this mode is used for power reduction. however, due to the relatively short t csm period for completing each data transfer, the active clock stop mode is generally not useful for power reduction but, may be used for short duration data flow control by the hyperbus master. 3.1 command-address bit assignments table 3.1 command-address bit definitions ca bit# bit name bit function 47 r/w# identifies the transaction as a read or write. r/w# = 1 indicates a read transaction r/w# = 0 indicates a write transaction 46 address space (as) indicates whether the read or write transaction a ccesses the memory or register spaces. as = 0 indicates memory space. as = 1 indicates the register space. the register space is used to access device id and configuration registers. 45 burst type indicates whether the burst will be linear or wrapped. burst type = 0 indicates wrapped burst burst type = 1 indicates linear burst 44-35 (64 mb) reserved reserved for future row address expansion. reserved bits should be set to 0 by the hyperbus master. 34-22 (64 mb) row address row component of the ta rget address: system word address bits a23-a9. 21-16 upper column address upper column component of the target ad dress: system word address bits a8-a3.
document number: 001-97964 rev. *e page 6 of 29 s27kl0641, s27ks0641 advance 3.2 read transactions note: 1. the latency code is the value loaded into configuration register bits cr0[7:4]. 3.3 write to memory space transactions when a linear burst write reaches the last address in the array, continuing the burst beyond the last address has undefined res ults. 15-3 reserved reserved for future column address expansion. reserved bits should be set to 0 by the hyperbus master. 2-0 lower column (word) address lower column component of the target address: system word address bits a2-0 selecting the starting word within a row. table 3.2 maximum operating frequency for latency code options latency code latency clocks maximum operating frequency (mhz) 0000 5 133 0001 6 166 0010 reserved na 0011 reserved na 0100 reserved na 0101 reserved na 0110 reserved na 0111 reserved na 1000 reserved na 1001 reserved na 1010 reserved na 1011 reserved na 1100 reserved na 1101 reserved na 1110 3 83 1111 4 100 table 3.1 command-address bit definitions (continued) ca bit# bit name bit function
document number: 001-97964 rev. *e page 7 of 29 s27kl0641, s27ks0641 advance 4. memory space when ca[46] is 0 a read or write tran saction accesses the dram memory array. 5. register space when ca[46] is 1 a read or write tr ansaction accesses the register space. note: 1. ca45 may be either 0 or 1 for either wrapped or linear read. ca45 must be 1 as only linear single word register writes are supported. 5.1 device identification registers there are two read only, non-volatile, word registers, that provide information on the device selected when cs# is low. the dev ice information fields identify: ? manufacturer ? type ? density ? row address bit count ? column address bit count table 4.1 memory space address map unit type count system word address bits ca bits notes rows within 64 mb device 8192 (rows) a21 - a9 34 - 22 row 1 (row) a8 - a3 21 - 16 512 (word addresses) 1kbytes half-page 8 (word addresses) a2 - a0 2 - 0 16 bytes table 5.1 register space address map register system address ? ? ? 31-27 26-19 18-11 10-3 ? 2-0 ca bits 47 46 45 44-40 39-32 31-24 23-16 15-8 7-0 identification register 0 (read only) c0h or e0h 00h 00h 00h 00h 00h identification register 1 (read only) c0h or e0h 00h 00h 00h 00h 01h configuration register 0 read c0h or e0h 00h 01h 00h 00h 00h configuration register 0 write 60h 00h 01h 00h 00h 00h configuration register 1 read c0h or e0h 00h 01h 00h 00h 01h configuration register 1 write 60h 00h 01h 00h 00h 01h table 5.2 id register 0 bit assignments bits function settings (binary) 15-14 reserved reserved 13 reserved 0 - default 12-8 row address bit count 00000 - one row address bit ... 11111 - thirty-two row address bits
document number: 001-97964 rev. *e page 8 of 29 s27kl0641, s27ks0641 advance 5.1.1 density and row boundaries the dram array size (density) of the device can be determined from the total number of system address bits used for the row and column addresses as indicated by the row address bit count and co lumn address bit count fields in the id0 register. for example : a 64 mbit hyperram has 9 column address bits and 13 row address bits for a total of 22 word address bits = 2 22 = 4 mwords = 8 mbytes. the 9 column address bits indicate that each row holds 2 9 = 512 words = 1 kbytes. the row address bit count indicates there are 8196 rows to be refreshed within each array refresh in terval. the row count is used in calculating the refresh interv al. 5.2 register space access register default values are loaded upon power-up or hardware reset. the registers can be altered at any time while the device i s in the standby state. loading a register is accomplished with a single 16-bit word write transaction as shown in figure 5.1 . ca[47] is zero to indicate a write transaction, ca[46] is a one to indica te a register space write, ca[45] is a o ne to indicate a linear write, lower order bits in the ca field indicate the register address. figure 5.1 loading a register notes: 1. the host must not drive rwds during a write to register space. 2. the rwds signal is driven by the memory during the command -address period based on whether the memory array is being refreshed. this refresh indication does not affect the writing of regist er data. rwds is driven immediately after cs# goes low, before ca[47:46] are received to indicate that the transaction is a write to register space, fo r which the rwds refresh indicat ion is not relevant. 3. the register value is always provided immediately after the ca value and is not dela yed by a refresh latency. 4. the the rwds signal returns to high impedance after the comma nd-address period. register data is never masked. both data bytes of the register data are loaded into the selected register. 7-4 column address bit count 0000 - one column address bit ... 1111 - sixteen column address bits 3-0 manufacturer 0000 - reserved 0001 - spansion 0010 to 1111 - reserved table 5.3 id register 1 bit assignments bits function settings (binary) 15-4 reserved 0000_0000_0000b (default) 3-0 device type 0000 - hyperram 0001 to 1111 - reserved table 5.2 id register 0 bit assignments (continued) bits function settings (binary) cs# ck# , ck rwds dq[7:0] command-address rd 47:40 39:32 31:24 23:16 15:8 7:0 15:8 7:0 host drives dq[7:0] with command-address and register data memory drives rwds with refresh indication
document number: 001-97964 rev. *e page 9 of 29 s27kl0641, s27ks0641 advance each register is written with a separate si ngle word write transaction. register writ e transactions have zero latency, the sing le word of data immediately follows the command-address. rwds is not driven by the host during the write because rwds is always driven by the memory during the ca cycles to indicate whether a memory array refresh is in progr ess. because a register space write goes directly to a register, rather t han the memory array, there is no initial write latency, related to an array refresh that may be in progress. in a register write, rwds is also not used as a data mask because both bytes of a register are always written and never masked. reserved register fields must be written with their default value. writing reserved fields with other than default values may p roduce undefined results. reading of a register is accomplished with a single 16 bit read tran saction with ca[46]=1 to select register space. if more than one word is read, the same register value is repeated in each word read. the ca[45] burst type is ? don?t care? because only a singl e register value is read. the content s of the register is returned in the same man ner as reading array data, with one or two late ncy counts, based on the state of rwds during the command-address period. the latency count is defined in the configuration register 0 read latency field (cr0[7:4]). 5.2.1 configuration register 0 configuration register 0 (cr0) is used to define the power m ode and access protocol operating conditions for the hyperram device. configurable ch aracteristics include: ? wrapped burst length (16, 32, 64, or 12 8-byte aligned and length data group) ? wrapped burst type ? legacy wrap (sequential access with wrap around within a selected length and aligned group) ? hybrid wrap (legacy wrap once then linear bu rst at start of the next sequential group) ? initial latency ? variable latency ? whether an array read or write transaction will use fixed or variable latency. if fixed latency is selected the memory will al ways indicate a refresh latency and delay the read data transfer acco rdingly. if variable latency is selected, latency for a refresh is only added when a refresh is required at the same time a new transaction is starting. ? output drive strength ? deep power down mode table 5.4 configuration register 0 bit assignments cr0 bit function settings (binary) 15 deep power down enable 1 - normal operation (default) 0 - writing 0 to cr[15] causes the device to enter deep power down 14-12 drive strength 000 - 34 ohms (default) 001 - 115 ohms 010 - 67 ohms 011 - 46 ohms 100 - 34 ohms 101 - 27 ohms 110 - 22 ohms 111 - 19 ohms 11-8 reserved 1 - reserved (default) reserved for future use. when writing this register, these bits should be set to 1 for future compatibility.
document number: 001-97964 rev. *e page 10 of 29 s27kl0641, s27ks0641 advance 5.2.1.1 wrapped burst a wrapped burst transaction accesses memory within a group of words aligned on a word boundary matching the length of the configured group. wrapped access groups can be configured as 16, 32, 64, or 128 bytes alignment and length. during wrapped transactions, access starts at the command-address selected location within t he group, continues to the end of the configured w ord group aligned boundary, then wraps around to the beginning location in the group, then continues back to the starting location. wrapped bursts are generally used for critical word firs t instruction or data cache line fill read accesses. 5.2.1.2 hybrid burst the beginning of a hybrid burst will wrap within the target address wrapped burst group length before continuing to the next ha lf- page of data beyond the end of the wrap group. continued access is in linear burst order until the transfer is ended by returni ng cs# high. this hybrid of a wrapped burst follow ed by a linear burst starting at the begi nning of the next burst group, allows multi ple sequential address cache lines to be filled in a single access. t he first cache line is filled starting at the critical word. t hen the next sequential line in memory can be read in to the cache while the first line is being processed. 7-4 initial latency 0000 - 5 clock latency 0001 - 6 clock latency (default) 0010 - reserved 0011 - reserved 0100 - reserved ... 1101 - reserved 1110 - 3 clock latency 1111 - 4 clock latency 3 fixed latency enable 0 - variable latency - 1 or 2 times initial latency depending on rwds during ca cycles. 1 - fixed 2 times initial latency (default) 2 hybrid burst enable 0: wrapped burst sequences to follow hybrid burst sequencing 1: wrapped burst sequences in legacy wrapped burst manner (default) 1-0 burst length 00 - 128 bytes 01 - 64 bytes 10- 16 bytes 11 - 32 bytes (default) table 5.5 cr0[2] control of wrapped burst sequence bit default value name 21 hybrid burst enable cr[2]= 0: wrapped burst sequences to follow hybrid burst sequencing cr[2]= 1: wrapped burst sequences in legacy wrapped burst manner table 5.4 configuration register 0 bi t assignments (continued) cr0 bit function settings (binary)
document number: 001-97964 rev. *e page 11 of 29 s27kl0641, s27ks0641 advance . table 5.6 example wrapped burst sequences burst selection burst type wrap boundary (bytes) start address (hex) address sequence (hex) (words) ca[45] cr0[2:0] 0000 hybrid 128 128 wrap once then linear xxxxxx03 03, 04, 05, 06, 07, 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c , 1d, 1e, 1f, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2a, 2b, 2c, 2d, 2e, 2f, 30, 31, 32 , 33, 34, 35, 36, 37, 38, 39, 3a, 3b, 3c, 3d, 3e, 3f, 00, 01, 02 (wrap complete, now linear beyond the end of the initial 128 byte wrap group) 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 4a, 4b, 4c, 4d, 4e, 4f, 50, 51, ... 0 001 hybrid 64 64 wrap once then linear xxxxxx03 03, 04, 05, 06, 07, 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c, 1d, 1e, 1f, 00, 01, 02, (wrap complete, now linear beyond the end of the initial 64 byte wrap group) 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2a, 2b, 2c, 2d, 2e, 2f, 30, 31, ... 0 001 hybrid 64 64 wrap once then linear xxxxxx2e 2e, 2f, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 3a, 3b, 3c, 3d, 3e, 3f, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2a, 2b, 2c, 2d, (wrap complete, now linear beyond the end of the initial 64 byte wrap group) 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 4a, 4b, 4c, 4d, 4e, 4f, 50, 51, ... 0 010 hybrid 16 16 wrap once then linear xxxxxx02 02, 03, 04, 05, 06, 07, 00, 01, (wrap complete, now linear beyond the end of the initial 16 byte wrap group) 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, ... 0 010 hybrid 16 16 wrap once then linear xxxxxx0c 0c, 0d, 0e, 0f, 08, 09, 0a, 0b, (wrap complete, now linear beyond the end of the initial 16 byte wrap group) 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, ... 0 011 hybrid 32 32 wrap once then linear xxxxxx0a 0a, 0b, 0c, 0d, 0e, 0f, 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, ... 0 011 hybrid 32 32 wrap once then linear xxxxxx1e 1e, 1f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c, 1d, ... 0 100 wrap 128 128 xxxxxx03 03, 04, 05, 06, 07, 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c , 1d, 1e, 1f, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2a, 2b, 2c, 2d, 2e, 2f, 30, 31, 32 , 33, 34, 35, 36, 37, 38, 39, 3a, 3b, 3c, 3d, 3e, 3f, 00, 01, 02, ... 0 101 wrap 64 64 xxxxxx03 03, 04, 05, 06, 07, 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c, 1d, 1e, 1f, 00, 01, 02, ... 0 101 wrap 64 64 xxxxxx2e 2e, 2f, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 3a, 3b, 3c, 3d, 3e, 3f, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2a, 2b, 2c, 2d, ... 0 110 wrap 16 16 xxxxxx02 02, 03, 04, 05, 06, 07, 00, 01, ... 0 110 wrap 16 16 xxxxxx0c 0c, 0d, 0e, 0f, 08, 09, 0a, 0b, ... 0 111 wrap 32 32 xxxxxx0a 0a, 0b, 0c, 0d, 0e, 0f, 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, ...
document number: 001-97964 rev. *e page 12 of 29 s27kl0641, s27ks0641 advance 5.2.1.3 initial latency memory space read and write transactions or register space read transactions require some initial latency to open the row selec ted by the command-address. this initial latency is t acc . the number of latency clocks needed to satisfy t acc depends on the hyperbus frequency and can vary from 3 to 6 clocks. the value in cr0[7:4] selects the number of clocks for initial latency. the default value is 6 clocks, allowing for operation up to a maximum frequency of 166mhz prior to the host system setting a lower initial latency value that may be more optimal for the system. in the event a distributed refresh is requ ired at the time a memory space read or write transaction or register space read transaction begins, the rwds signal goes high during the command- address to indicate that an additional initial latency is bein g inserted to allow a refresh operation to complete before opening the selected row. register space write transactions always have zero initial la tency. rwds may be high or low during the command-address period. the level of rwds during the command-address period does not affect the placement of re gister data immediately after th e command-address, as there is no initial latency needed to capture the register data. a refresh op eration may be performed in th e memory array in parallel with the capture of register data. 5.2.1.4 fixed latency a configuration register option bit cr0[3] is provided to make al l memory space read and write tran sactions or register space r ead transactions require the same initial latency by always driving rw ds high during the command-addre ss to indicate that two initi al latency periods are required. this fixed initial latency is inde pendent of any need for a distribut ed refresh, it simply provid es a fixed (deterministic) initial latency for all of these transaction types . the fixed latency option may simplify the design of some hy perbus memory controllers or ensure deterministic transaction performanc e. fixed latency is the default por or reset configuration. th e system may clear this configurat ion bit to disable fixed latenc y and allow variable initial late ncy with rwds driven high only when additional latency for a refresh is required. 5.2.1.5 drive strength dq signal line loading, length, and impedance vary depending on each system design. configuration register bits cr0[14:12] provide a means to adjust the dq [7:0] signal out put impedance to customize the dq signa l impedance to the system conditions to minimize high speed signal behaviors such as overshoot, unders hoot, and ringing. the default po r or reset configuration value i s 000b to select the mid point of the available output impedance options. the impedance values shown are typical for both pull-up and pull- down drivers at typical silicon process conditions, nominal operating voltage (1.8vor 3v) and 50c. the impedance values may va ry by up to 80% from the typical values depending on the process, voltage, and temperature (pvt) conditions. impedance will increase with slower process, lower voltage, or higher temperature. impedance will decrease with faster process, higher voltage, or lower temperature. each system design should evaluate the data signal integrity across the operating volt age and temperature ranges to select the best drive strength settings for the operating conditions. 0 111 wrap 32 32 xxxxxx1e 1e, 1f, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1a, 1b, 1c, 1d, ... 1 xxx linear linear burst xxxxxx03 03, 04, 05, 06, 07, 08, 09, 0a, 0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15, 16, 17, 18, ... table 5.6 example wrapped burst sequences (continued) burst selection burst type wrap boundary (bytes) start address (hex) address sequence (hex) (words) ca[45] cr0[2:0]
document number: 001-97964 rev. *e page 13 of 29 s27kl0641, s27ks0641 advance 5.2.1.6 deep power down when the hyperram device is not needed for system operation, it may be placed in a ve ry low power consuming mode called deep power down (dpd), by writing 0 to cr0[15]. when cr0[15] is cleared to 0, the device enters the dpd mode within t dpdin time and all refresh operations stop. the data in ram is lost, (becomes invalid without refresh) during dpd mode. the next access to the device driving cs# low then high, por, or a reset will cause the device to exit dpd mode. returning to standby mode requires t dpdout time. for additional details see section 6.1.3, deep power down on page 15 . 5.2.2 configuration register 1 configuration register 1 (cr1) is used to define the distributed re fresh interval for this hyperram device. the core dram array requires periodic refresh of all bits in the array. this c an be done by the host system by read ing or writing a location in eac h row within a specified time limit. the read or write access copies a row of bits to an internal buffer. at the end of the access th e bits in the buffer are written back to the row in memory, thereby rechargi ng (refreshing) the bits in th e row of dram memory cells. however, the host system generally has better things to do than to periodically read every row in memory and keep track that ea ch row is visited within the required refresh interval for the enti re memory array. the hyperram family devices include self-refre sh logic that will refresh rows autom atically so that the host system is relieved of the need to refresh the memory . the automatic refre sh of a row can only be done when the memory is not being actively read or writ ten by the host system. the refresh logic waits for the end of any active read or write before doing a refresh, if a refres h is needed at that time. if a new read or write begins before t he refresh is completed, the memory will drive rwds high during the command- address period to indicate that an additional initial latency time is required at the start of the new access in order to allo w the refresh operation to complete before starting the new acc ess. the required refresh interval for the entire memo ry array varies with temperature as shown in table 5.7, array refresh interval per temperature on page 13 . this is the time within which all rows must be re freshed. refresh of all rows could be done as a single batch of accesses at the beginning of each interval, in groups (burst refresh) of several rows at a time, spread throughout eac h interval, or as single row refreshes even ly distributed throughout the in terval. the self-refresh logic distributes single row refresh operations throughout the interval so that the memory is not bu sy doing a burst of refresh operati ons for a long period, such t hat the burst refresh would delay host access for a long period. table 5.7 array refresh interval per temperature device temperature (c) array refresh interval (ms) array rows recommended t cms (s) 85 64 8192 4 105 16 8192 1 table 5.8 configuration register 1 bit assignments cr1 bit function settings (binary) 15-2 reserved 000000h ? reserved (default) reserved for future use. when writing this register, these bits should be cleared to 0 for future compatibility. 1-0 distributed refresh interval 10b ? default 4 s for industrial temperature range devices 1 s for industrial plus temperature range devices 11b ? 1.5 times default 00b ? 2 times default 01b ? 4 times default
document number: 001-97964 rev. *e page 14 of 29 s27kl0641, s27ks0641 advance the distributed refresh method r equires that the host does not do burst transactions that are so lo ng as to prevent the memory from doing the distributed refreshes when they are needed. this sets an upper limit on the length of read and write transactions so that the refresh logic can insert a refres h between transactions. this limit is called the cs# low maximum time (t cms ). the t cms value is determined by the array refresh interval divided by the number of rows in the array, then reducin g this calculation by half to ensure that a distributed refresh interval canno t be entirely missed by a maximum lengt h host access starting immediately before a distributed refresh is needed. because t cms is set to half the required distributed refres h interval, any series of maximum length host accesses that delay refresh operations will be catching up on re fresh operations at twice the rate required by the refresh inte rval divided by the number of rows. the host system is required to respect the t cms value by ending each transaction before violating t cms . this can be done by host memory controller logic splitting l ong transactions when reaching the t cms limit, or by host system hardware or software not performing a single read or write transa ction that would be longer than t cms . as noted in table 5.7, array refresh interval per temperature on page 13 the array refresh interval is longer at lower temperatures such that t cms could be increased to allow longer transactions. the host system can either use the t cms value from the table for the maximum operating temperature or, may dete rmine the current operating tem perature from a temperature sensor in the system in order to set a longer distributed refresh interval. the host system may also effectively increase the t cms value by explicitly taking responsibility for performing all refresh and doing burst refresh reading of multiple sequential rows in order to catch up on distributed refreshes missed by longer transactions.
document number: 001-97964 rev. *e page 15 of 29 s27kl0641, s27ks0641 advance hyperram hardware interface for the general description of the hyperbus hardware interface of hyperflash memories refer to the hyperbus specification. the following section describes hyperram device dependent aspects of hardware interface. 6. interface states 6.1 power conservation modes 6.1.1 interface standby standby is the default, low power, state for the interface while the device is not selected by the host for data transfer (cs#= high). all inputs, and outputs other than cs# and reset# are ignored in this state. 6.1.2 active clock stop the active clock stop mode reduces device interface energy consumption to the i cc6 level during the data transfer portion of a read or write operation. the device automatically ena bles this mode when clo ck remains stable for t acc + 30 ns. while in active clock stop mode, read data is latched and always driven onto the data bus. i cc6 shown in section 7.4, dc characteristics on page 18 . active clock stop mode helps reduce current consumption when th e host system clock has stopped to pause the data transfer. even though cs# may be low throughout these extended data transfer cycles, the memory device host interface will go into the active clock stop current level at t acc + 30 ns. this allows the device to transition into a lower current mode if the data transfer is stalled. active read or write current will resume once the data transfer is restarted with a toggling clock. the active clock s top mode must not be used in violation of the t csm limit. cs# must go high before t csm is violated. 6.1.3 deep power down in the deep power down (dpd) mode, current consum ption is driven to the lowest possible level (i dpd ). dpd mode is entered by writing a 0 to cr0[15]. the device reduces power within t dpdin time and all refresh operations st op. the data in memory space is lost, (becomes invalid without refresh) du ring dpd mode. the next access to the devi ce, driving cs# low then high, will cause t he device to exit dpd mode. a read or write transaction used to drive cs# low then high to exit dp d mode is a dummy transaction th at is ignored by the device. also, por, or a hardware reset will caus e the device to exit dpd mode. only the cs# and reset# signal s are monitored during dpd mode. returning to standby mode following a dummy transaction or reset requires t dpdout time. returning to standby mode following a por requires t vcs time, as with any other por. following the exit from dpd due to any of these events, the device is in th e same state as following por. table 6.1 deep power down timing parameters parameter description min max unit t dpdin deep power down cr0[15]=0 regist er write to dpd power level 10 ? s t dpdcsl length of cs# low period to cause an exit from deep power down 200 ? ns t dpdout cs# low then high to standby wakeup time ? 150 s
document number: 001-97964 rev. *e page 16 of 29 s27kl0641, s27ks0641 advance figure 6.1 deep power down entry timing figure 6.2 deep power down cs# exit timing cs# ck# , ck dq[7:0] phase write command-address cr value enter dpd mode dpd mode t dpdin cs# ck# , ck dq[7:0] phase dpd mode dummy transaction to exit dpd exit dpd mode standby new transaction t dpdout t dpdcsl
document number: 001-97964 rev. *e page 17 of 29 s27kl0641, s27ks0641 advance 7. electrical specifications 7.1 absolute maximum ratings storage temperature plastic packages ? 65 c to +150 c ambient temperature with power applied ? 65c to +115 c voltage with respect to ground all signals ( 1 ) ? 0.5v to +(v cc + 0.5v) output short circuit current ( 2 ) 100 ma v cc ? 0.5v to +4.0v notes: 1. minimum dc voltage on input or i/o signal is ? 1.0v. during voltage transitions, input or i/o signals may undershoot v ss to -1.0v for periods of up to 20 ns. see figure 7.1 . maximum dc voltage on input or i/o signals is v cc +1.0v. during voltage transitions, input or i/o signals may overshoot to v cc +1.0v for periods up to 20 ns. see figure 7.2 . 2. no more than one output may be shorted to ground at a time . duration of the short circuit should not be greater than one second. 3. stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only; functional operation of the device at these or any other cond itions above those indicated in the operational sections of this data sheet is not implied. exposure of the device to absolute maximum rating conditions for extended periods may affect device reliability. 7.1.1 input sign al overshoot during dc conditions, input or i/o signals should remain equal to or between v ss and v dd . during voltage transitions, inputs or i/os may overshoot v ss to ? 1.0v or overshoot to v dd +1.0v, for periods up to 20 ns. figure 7.1 maximum negative overshoot waveform figure 7.2 maximum positive overshoot waveform v ss q to v cc q - 1.0v 20 ns v cc q + 1.0v 20 ns v ss q to v cc q
document number: 001-97964 rev. *e page 18 of 29 s27kl0641, s27ks0641 advance 7.2 latchup characteristics note: 1. excludes power supplies v cc /v ccq . test conditions: v cc = v ccq = 1.8 v, one connection at a time tested, connections not being tested are at v ss . 7.3 operating ranges operating ranges define those limit s between which the functionalit y of the device is guaranteed. 7.3.1 temperature ranges ambient temperature (t a ) industrial ?40 c to +85 c industrial plus ?40 c to +105 c 7.3.2 1.8v power supply voltages v cc and v ccq 1.7v to 1.95v 7.3.3 3.0v power supply voltages v cc and v ccq 2.7v to 3.6v 7.4 dc characteristics table 7.1 latchup specification description min max unit input voltage with respect to v ss q on all input only connections ? 1.0 v ccq + 1.0 v input voltage with respect to v ss q on all i/o connections ? 1.0 v ccq + 1.0 v v ccq current ? 100 +100 ma table 7.2 dc characteristics (cmos compatible) parameter description te st conditions min typ (1) max unit i li input leakage current 3v device reset signal high only v in = v ss to v cc , v cc = v cc max ??? 0.1 a i li input leakage current 1.8v device reset signal high only v in = v ss to v cc , v cc = v cc max ??? 0.1 a i li input leakage current 3v device reset signal low only (2) v in = v ss to v cc , v cc = v cc max ?? +20.0 a i li input leakage current 1.8v device reset signal low only (2) v in = v ss to v cc , v cc = v cc max ?? +20.0 a i cc1 v cc active read current cs# = v il , @166 mhz, v cc = 1.9v ? 20 60 ma ? cs# = v il , @100 mhz, v cc = 3.6v ? 20 35 ma i cc2 v cc active write current cs# = v il , @166 mhz, v cc = 1.9v ? 15 60 ma ? cs# = v il , @100 mhz, v cc = 3.6v ? 15 35 ma
document number: 001-97964 rev. *e page 19 of 29 s27kl0641, s27ks0641 advance note: 1. not 100% tested. 2. reset# low initiates exits from dpd mode and initiate s the draw of i cc5 reset current, making i li during reset# low insignificant. 7.4.1 capacitance characteristics notes: 1. these values are guaranteed by design and are tested on a sample basis only. 2. contact capacitance is measured according to jep147 procedur e for measuring capacitance using a vector network analyzer. v cc, v cc q are applied and all other signals (except the signal under test) floating. dq?s should be in the high impedance state. 3. note that the capacitance values for the ck, ck#, rwds and dqx signals must have similar capacitance values to allow for signal propagati on time matching in the system. the capa citance value for cs# is not as crit ical because there are no critical timings between cs# going active (low) and data being presented on the dqs bus. i cc4i v cc standby current for industrial ( ? 40 c to +85 c) cs#, v cc = v cc max, ? 135 200 a i cc4ip v cc standby current for industrial plus ( ? 40 c to +105 c) cs#, v cc = v cc max ? 135 300 a i cc5 reset current cs# = v ih , reset# = v il , v cc = v cc max ? 10 20 ma i cc6i active clock stop current for industrial ( ? 40 c to +85 c) cs# = v il , reset# = v ih , v cc = v cc max ? 5.3 8 ma i cc6ip active clock stop current for industrial plus( ? 40 c to +105 c) cs# = v il , reset# = v ih , v cc = v cc max ? 5.3 12 ma i cc7 v cc current during power up (1) cs#, = h , v cc = v cc max, v cc = v cc q = 1.95v or 3.6v (note 7.4.1) ?? 35 ma i dpd deep power down current 3v 85c cs#, v cc = 3.6v, t a = 85 c ?? 20 a i dpd deep power down current 1.8v 85c cs#, v cc = 1.9v, t a = 85 c ?? 10 a i dpd deep power down current 3v 105c cs#, v cc = 3.6v, t a = 105 c ?? 40 a i dpd deep power down current 1.8v 105c cs#, v cc = 1.9v, t a = 105 c ?? 20 a table 7.3 1.8v capacitive characteristics description parameter min max unit input capacitance (ck, ck#, cs#) ci 3 4.5 pf delta input capacitance (ck, ck#) cid ? 0.25 pf output capacitance (rwds) co 3 4 pf io capacitance (dqx) cio 3 4 pf io capacitance delta (dqx) ciod ? 0.5 pf table 7.2 dc characteristics (cmos compatible) (continued) parameter description te st conditions min typ (1) max unit
document number: 001-97964 rev. *e page 20 of 29 s27kl0641, s27ks0641 advance notes: 1. these values are guaranteed by design and are tested on a sample basis only. 2. contact capacitance is measured according to jep147 procedur e for measuring capacitance using a vector network analyzer. v cc, v cc q are applied and all other signals (except the signal under test) floating. dq?s should be in the high impedance state. 3. note that the capacitance values for the ck, rwds and dqx sign als must have similar capacitanc e values to allow for signal propagation time matching in the system. the capacitance value for cs# is not as critical because there are no critical timings between cs# going active (low) and data being presented on the dqs bus. 7.5 power-up initialization hyperram family products include an on-chip voltage sens or used to launch the power-up initialization process. v cc and v cc q must be applied simultaneously. when the power supply reaches a stable level at or above v cc (min), the device will require t vcs time to complete its self-initialization process. the device must not be selected during power-up. cs# must follow the voltage applied on v cc q until v cc (min) is reached during power-up, and then cs# must remain high for a further delay of t vcs . a simple pull-up resistor from v cc q to chip select (cs#) can be used to insure safe and proper power-up. if reset# is low during power up, the device delays start of the t vcs period until reset# is high. the t vcs period is used primarily to perform refresh operations on the dram array to initialize it. when initialization is complete, the device is ready for normal operation. figure 7.3 power-up with reset# high table 7.4 3.0v capacitive characteristics description parameter min max unit input capacitance (ck, cs#) ci 3 4.5 pf output capacitance (rwds) co 3 4 pf io capacitance (dqx) cio 3 4 pf io capacitance delta (dqx) ciod ? 0.5 pf vcc_vccq cs# reset# t vcs v cc minimum device access allowed
document number: 001-97964 rev. *e page 21 of 29 s27kl0641, s27ks0641 advance figure 7.4 power-up with reset# low notes: 1. bus transactions (read and write) are not allowed during the power-up reset time (t vcs ). 2. v cc q must be the same voltage as v cc . 3. v cc ramp rate may be non-linear. 7.6 power down for the general description of the hyperbus interface power down specifications refer to the hype rbus specification. the follow ing section describes hyperram device dependent aspects of power down specifications. note: 1. v cc ramp rate can be non-linear. note: 1. v cc ramp rate can be non-linear. table 7.5 power up and reset parameters parameter description min max unit v cc 1.8v v cc power supply 1.7 1.95 v v cc 3v v cc power supply 2.7 3.6 v t vcs v cc and v cc q ? minimum and reset# high to first access ? 150 s table 7.6 1.8v power-down voltage and timing symbol parameter min max unit v cc v cc power supply 1.7 1.95 v v lko v cc lock-out below which re-initialization is required 1.7 ? v v rst v cc low voltage needed to ensure initialization will occur 0.8 ? v t pd duration of v cc ? v rst 30 ? s table 7.7 3.0v power-down voltage and timing symbol parameter min max unit v cc v cc power supply 2.7 3.6 v v lko v cc lock-out below which re-initialization is required 2.7 ? v v rst v cc low voltage needed to ensure initialization will occur 0.8 ? v t pd duration of v cc ? v rst 50 ? s vcc_vccq cs# reset# t vcs v cc minimum device access allowed
document number: 001-97964 rev. *e page 22 of 29 s27kl0641, s27ks0641 advance 7.7 hardware reset the reset# input provides a hardware method of returning the device to the standby state. during t rph the device will draw i cc5 current. if reset# contin ues to be held low beyond t rph , the device draws cmos standby current (i cc4 ). while reset# is low (during t rp ), and during t rph , bus transactions are not allowed. a hardware reset will: ? cause the configuration registers to return to their default values, ? halt self-refresh operat ion while reset# is low, ? and force the device to exit the deep power down state. after reset# returns high, the self-refresh operation will resume. because self-refres h operation is stopped during reset# low, and the self-refresh row counter is reset to its default value, some rows may not be refreshed within the required array refres h interval per table 5.7, array refresh interval per temperature on page 13 . this may result in the loss of dram array data during or immediately following a hardware reset. the host system should assume dram array data is lost after a hardware reset and reload any required data. figure 7.5 hardware reset timing diagram table 7.8 power up and reset parameters parameter description min max unit t rp reset# pulse width 200 ? ns t rh time between reset# (high) and cs# (low) 200 ? ns t rph reset# low to cs# low 400 ? ns reset# cs# t rp t rh t rph t vcs - if reset# low > t rp max
document number: 001-97964 rev. *e page 23 of 29 s27kl0641, s27ks0641 advance 8. timing specifications for the general description of the hyperbus interface timing spec ifications refer to the hyperbus specification. the following section describes hyperram device dependent as pects of timing specifications. 8.1 ac characteristics 8.1.1 read transactions table 8.1 hyperram specific 1.8v read timing parameters note: 1. sampled, not 100% tested. table 8.2 hyperram specific 3.0v read timing parameters note: 1. sampled, not 100% tested. 8.1.2 write transactions table 8.3 1.8v write timing parameters note: 1. sampled, not 100% tested. parameter symbol 166 mhz 133 mhz 100 mhz (1) unit min max min max min max read-write recovery time t rwr 36 ? 37.5 ? 40 ? ns refresh time t rfh 36 ? 37.5 ? 40 ? ns access time t acc 36 ? 37.5 ? 40 ? ns chip select maximum low time ? industrial temperature t csm ? 4.0 ? 4.0 ? 4.0 s chip select maximum low time ? industrial plus temperature ? 1.0 ? 1.0 ? 1.0 s parameter symbol 100 mhz unit min max read-write recovery time t rwr 40 ? ns refresh time t rfh 40 ? ns access time t acc 40 ? ns chip select maximum low time ? industrial temperature t csm ? 4.0 s chip select maximum low time ? industrial plus temperature ? 1.0 s parameter symbol 166 mhz 133 mhz 100 mhz (1) unit min max min max min max read-write recovery time t rwr 36 ? 37.5 ? 40 ? ns access time t acc 36 ? 37.5 ? 40 ? ns refresh time t rfh 36 ? 37.5 ? 40 ? ns chip select maximum low time ?? industrial temperature t csm ? 4.0 ? 4.0 ? 4.0 s chip select maximum low time ? industrial plus temperature ? 1.0 ? 1.0 ? 1.0 s
document number: 001-97964 rev. *e page 24 of 29 s27kl0641, s27ks0641 advance table 8.4 3.0v write timing parameters note: 1. sampled, not 100% tested. parameter symbol 100 mhz unit min max read-write recovery time t rwr 40 ? ns access time t acc 40 ? ns refresh time t rfh 40 ? ns chip select maximum low time ? industrial temperature t csm ? 4.0 s chip select maximum low time ? industrial plus temperature ? 1.0 s
document number: 001-97964 rev. *e page 25 of 29 s27kl0641, s27ks0641 advance 9. physical interface see the hyperbus specification for footprint and the 6 ? 8 ? 1mm (vaa024) physical package diagram. 10. ordering information 10.1 ordering part number the ordering part number is formed by a valid combination of the following: s27ks 064 1 dp b h i 02 0 packing type 0 = tray 3 = 13? tape and reel model number (additional ordering options) 02 = standard 6 ? 8 ? 1.0 mm package (vaa024) temperature range i = industrial (?40 c to + 85 c) v = industrial plus (?40 c to + 105 c) package materials h = low-halogen, lead (pb)-free package type b = 24-ball fbga, 1.00 mm pitch (5x5 ball footprint) speed da = 100 mhz dp = 166 mhz device technology 1 = 0.063 m dram process technology density 064 = 64 mb device family s27ks cypress memory 1.8v-only, hyperram self-refresh dram s27kl cypress memory 3.0v-only, hyperram self-refresh dram
document number: 001-97964 rev. *e page 26 of 29 s27kl0641, s27ks0641 advance 10.2 valid combinations the recommended combinations table lists configurations planned to be available in volume. the table below will be updated as new combinations are released. consult your local sales represent ative to confirm availability of specific combinations and to check on newly released combinations. device family density technology speed package, material and temperature model number packing type ordering part numb er package marking s27kl 064 1 da bhi 02 0 s27kl0641dabhi020 7kl0641dahi02 s27kl 064 1 da bhi 02 3 S27KL0641DABHI023 7kl0641dahi02 s27kl 064 1 da bhv 02 0 s27kl0641dabhv020 7kl0641dahv02 s27kl 064 1 da bhv 02 3 s27kl0641dabhv023 7kl0641dahv02 s27ks 064 1 dp bhi 02 0 s27ks0641dpbhi020 7ks0641dphi02 s27ks 064 1 dp bhi 02 3 s27ks0641dpbhi023 7ks0641dphi02 s27ks 064 1 dp bhv 02 0 s27ks0641dpbhv020 7ks0641dphv02 s27ks 064 1 dp bhv 02 3 s27ks0641dpbhv023 7ks0641dphv02
document number: 001-97964 rev. *e page 27 of 29 s27kl0641, s27ks0641 advance 11. errata this section describes the errata for the s27kl0641 and s27ks06 41 family. details include errata trigger conditions, scope of impact, available workarounds, and silicon revision applicability. contact your local cypress sales representative if you have questions. s27kl0641 and s27ks0641 qualification status product status: sampling s27kl0641, s27ks0641 errata summary the following table defines the errata applicability to available s27kl0641 and s27ks0641s family devices. 1. variable latency mode does not function ? problem definition the rwds signal may not correctly indicate when additional initial latency is being inserted when the device is configured for variable initial latency. ? parameters affected initial latency count. ? trigger condition use of variable latency configuration by setting configuration register 0 bit 3 to 0. ? scope of impact intermittent failure of read data to start transferring on the bus when expected, based on th e latency count indicated by rwds during the command-address cycles. ? workaround use the default fixed latency configuration or use rwds transit ions as the indication for when to capture the first and following read data transfers. ? fix status will be fixed in production silicon. part number device characteristics s27kl0641, s27ks0641 hyperram self-refresh dram items part number silicon revision fix status [ 1 ]. variable latency mode does not function s27kl0641 s27ks0641 *b will be fixed in production silicon
document number: 001-97964 rev. *e page 28 of 29 s27kl0641, s27ks0641 advance 12. revision history document history page document title: s27kl0641, s27ks0641, hyperram ? self-refresh dram 3.0v/1.8v 64 mb (8 mb) document number: 001-97964 rev. ecn no. orig. of change submission date description of change ** ? mamc 05/01/2015 initial release *a ? mamc 06/05/2015 read transactions: maximum operating frequency for latency code options table: updated ?latency code? 0010 values device identification registers: updated ?id register 1 bit assignments? table electrical specifications: updated am bient temperature with power applied hyperram hardware interface: updated the following: power-on reset: removed section power down: removed section dc characteristics (cmos compatible) table: updated i cc5 , i cc6i , and i cc6ip test conditions electrical specifications/power down: 1.8v power-down voltage and timing table: changed v rst and t pd min 3.0v power-down voltage and timing table: changed v rst and t pd min key to switching waveforms: removed section ac test conditions: removed section ac characteristics: updated section hyperbus specification: removed section. refer to the hyperbus specification for all non-device specific information on the hyperbus interface. *b ? mamc 07/10/2015 physical interface: updated section. ordering information: updated valid combinations table. *c 4854266 mamc 07/29/2015 updated to cypress template *d 5041839 mamc 12/08/2015 updated dc characteristics : added i dpd for t a = 105c updated i li for the reset# input. *e 5155616 rysu 03/01/2016 added errata .
document number: 001-97964 rev. *e revised march 01, 2016 page 29 of 29 cypress ? , spansion ? , mirrorbit ? , mirrorbit ? eclipse?, ornand?, hyperbus?, hyperflash?, and combinations thereof, are trademarks and registered trademarks of cypress semic onductor corp. s27kl0641, s27ks0641 advance ? cypress semiconductor corporation 2015-2016. this document is the property of cypress semiconductor corporation and its subsi diaries, including spansion llc ("cypress"). this document, including any software or firmware included or referenced in this document ("software"), is owned by cypress under the intellec tual property laws and treaties of the united states and other countries worldwide. cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragr aph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. if the software is not accompanied by a license agreement and you do not otherwise have a writte n agreement with cypress governing the use of the software, then cypress hereby grants you under its copyright rights in the software, a personal, non-exclusive, nontransferable license (without the r ight to sublicense) (a) for software provided in source code form, to modify and reproduce the software solely for use with cypress hardware products, only internally within your organization, and (b) to distribute the software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on cypress hardware product units. cypress also gran ts you a personal, non-exclusive, nontransferable, license (without the right to sublicense) under those claims of cypress's patents that are infringed by the software (as provided by cypress, unmodified) to make, use, distribute, and import the software solely to the minimum extent that is necessary for you to exercise your rights under the copyright license granted in the previous sentence. any oth er use, reproduction, modification, translation, or compilation of the software is prohibited. cypress makes no warranty of any kind, express or implied, with regard to this document or any software, including, but not lim ited to, the implied warranties of merchantability and fitness for a particular purpose. cypress reserves the right to make changes to this document without further notice. cypress does not assume any liability arising out of the application or use of an y product or circuit described in this document. any informati on provided in this document, including any sample design information or programming code, is provided only for reference purposes. it is the responsibility of the user of this document to properly d esign, program, and test the functionality and safety of any application made of this information and any resulting product. cypress products are not designed, intended, or authorized for use as crit ical components in systems designed or intended for the operation of weapons, weapons systems, nuclear installations, life-support de vices or systems, other medical devices or systems (including r esuscitation equipment and surgical implants), pollution control or hazardous substances management, or other uses where the failure of the device or system could cause personal injury, death, or property damage ("unintended uses"). a critical component is any component of a device or system whose failure to perform can be reasonably expected to cause the failure of the device or syste m, or to affect its safety or effectiv eness. cypress is not liable, in whole or in part, and company shall and hereby does release cypress from any claim, damage, or other liability arising from or relate d to all unintended uses of cypress products. company shall indemnify and hold cypress harmless from and against all claims, costs, damages, and other liabilities, including claims for personal inj ury or death, arising from or related to any unintended uses of cypress products. cypress, the cypress logo, spansion, the spansion logo, and combinations thereof, psoc, capsense, ez-usb, f-ram, and traveo are trademarks or registered trad emarks of cypress in the united states and other countries. for a more complete list of cypre ss trademarks, visit cypress.com. other names and brands may be claimed as property of their respective owners. sales, solutions, and legal information worldwide sales and design support cypress maintains a worldwide network of offices, solution center s, manufacturer?s representatives, and distributors. to find t he office closest to you, visit us at cypress locations . products arm ? cortex ? microcontrollers cypress.com/arm automotive cypress.com/automotive clocks & buffers cypress.com/clocks interface cypress.com/interface lighting & power control cypress.com/powerpsoc memory cypress.com/memory psoc cypress.com/psoc touch sensing cypress.com/touch usb controllers cypress.com/usb wireless/rf cypress.com/wireless psoc ? solutions cypress.com/psoc psoc 1 | psoc 3 | psoc 4 | psoc 5lp cypress developer community community | forums | blogs | video | training technical support cypress.com/support

▲Up To Search▲

Price & Availability of S27KL0641DABHI023

	To Download S27KL0641DABHI023 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .